Designs for remaining minimum system information (RMSI) control resource set (CORESET) and other system information (OSI) coreset

ABSTRACT

Certain aspects of the present disclosure provide techniques and apparatus relating to designs for the remaining minimum system information (RMSI) control resource set (CORESET) and the other system information (OSI) CORESET. In certain aspects, a wireless communication device (e.g., user equipment) is enabled to determine the location of Type0-PDCCH common search space CORESET and the OSI CORESET in the frequency and time domains based on the location of the synchronization signal block (SSB) transmissions in the frequency and time domains. Determining the location of the RMSI CORESET and the OSI CORESET frequency and time resources enables the UE to receive the RMSI CORESET and the OSI CORESET, respectively.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Application Ser. No.62/588,245 entitled “DESIGNS FOR REMAINING MINIMUM SYSTEM INFORMATION(RMSI) CONTROL RESOURCE SET (CORESET) AND OTHER SYSTEM INFORMATION (OSI)CORESET,” which was filed Nov. 17, 2017. The aforementioned applicationis herein incorporated by reference in its entirety.

FIELD

Aspects of the present disclosure relate generally to wirelesscommunications systems, and more particularly, to designs for remainingminimum system information (RMSI) control resource set (CORESET) andother system information (OSI) CORESET.

BACKGROUND

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, data,messaging, broadcasts, etc. The systems may employ multiple-accesstechnologies capable of supporting communication with multiple users bysharing available system resources (e.g., bandwidth and transmit power).Examples of such multiple-access systems include 3rd GenerationPartnership Project (3GPP) Long Term Evolution (LTE) systems, LTEAdvanced (LTE-A) systems, code division multiple access (CDMA) systems,time division multiple access (TDMA) systems, frequency divisionmultiple access (FDMA) systems, orthogonal frequency division multipleaccess (OFDMA) systems, single-carrier frequency division multipleaccess (SC-FDMA) systems, and time division synchronous code divisionmultiple access (TD-SCDMA) systems.

In some examples, a wireless multiple-access communication system mayinclude a number of base stations (BSs) that each can simultaneouslysupport communication for multiple communication devices, otherwiseknown as user equipment (UEs). In LTE or LTE-A network, a set of one ormore base stations may define an e NodeB (eNB). In other examples (e.g.,in a NR, next generation or 5G network), a wireless multiple accesscommunication system may include a number of distributed units (DUs)(e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smartradio heads (SRHs), transmission reception points (TRPs), etc.) incommunication with a number of central units (CUs) (e.g., central nodes(CNs), access node controllers (ANCs), etc.), where a set of one or moredistributed units, in communication with a central unit, may define anaccess node (e.g., a new radio base station (NR BS), a new radio node-B(NR NB), a network node, 5G NB, a Next Generation Node B (gNB), etc.).BS or DU may communicate with a set of UEs on downlink channels (e.g.,for transmissions from a BS or to a UE) and uplink channels (e.g., fortransmissions from a UE to a BS or DU).

These multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent wireless devices to communicate on a municipal, national,regional, and even global level. An example of an emergingtelecommunication standard is new radio (NR), for example, 5G radioaccess. NR is a set of enhancements to the LTE mobile standardpromulgated by Third Generation Partnership Project (3GPP). It isdesigned to better support mobile broadband Internet access by improvingspectral efficiency, lowering costs, improving services, making use ofnew spectrum, and better integrating with other open standards usingOFDMA with a cyclic prefix (CP) on the downlink (DL) and on the uplink(UL) as well as support beamforming, multiple-input multiple-output(MIMO) antenna technology, and carrier aggregation.

However, as the demand for mobile broadband access continues toincrease, there exists a need for further improvements in NR technology.Preferably, these improvements should be applicable to othermulti-access technologies and the telecommunication standards thatemploy these technologies.

BRIEF SUMMARY

The systems, methods, and devices of the disclosure each have severalaspects, no single one of which is solely responsible for its desirableattributes. Without limiting the scope of this disclosure as expressedby the claims which follow, some features will now be discussed briefly.After considering this discussion, and particularly after reading thesection entitled “Detailed Description” one will understand how thefeatures of this disclosure provide advantages that include improvedcommunications between access points and stations in a wireless network.

Certain aspects of the present disclosure generally relate to designsfor the remaining minimum system information (RMSI) control resource set(CORESET) and the other system information (OSI) CORESET.

Certain aspects of the present disclosure provide a method for wirelesscommunications by a user equipment (UE). The method includes receiving aType0-physical downlink control channel (PDCCH) common search spacecontrol resource set (CORESET) configuration and a physical resourceblock (PRB) grid offset in a physical broadcast channel (PBCH) carriedby a synchronization signal block (SSB), the Type0-PDCCH common searchspace CORESET configuration comprising an indication indicative of oneor more offset values corresponding to one or more offsets relating tofrequency locations of Type0-PDCCH common search space CORESET resourceblocks (PRBs) relative to frequency locations of PRBs of the SSB. Themethod also includes aligning a PRB grid of SSB with a PRB grid ofType0-PDCCH common search space CORESET by applying the PRB grid offset.The method also includes mapping the indication to the one or moreoffset values using a mapping stored by the UE. The method also includesby determining the frequency locations of the Type0-PDCCH common searchspace CORESET PRBs based on the one or more offset values and thefrequency locations of the SSB PRBs. The method also includes receivingType0-PDCCH in the Type0-PDCCH common search space CORESET.

Certain aspects of the present disclosure provide a method for wirelesscommunications by a user equipment (UE). Certain aspects of the presentdisclosure provide a method for wireless communications by a userequipment (UE). The method includes determining time locations ofType0-physical downlink control channel (PDCCH) common search spacecontrol resource set (CORESET) in a physical downlink shared channel(PDSCH). The method further includes determining time locations ofType0a-physical downlink control common search space CORESET in thePDSCH based on the frequency locations of the Type0-PDCCH common searchspace CORESET. The method further includes receiving the Type0a-PDCCHcommon search space CORESET.

Aspects generally include methods, apparatus, systems, computer readablemediums, and processing systems, as substantially described herein withreference to and as illustrated by the accompanying drawings. Numerousother aspects are provided.

To the accomplishment of the foregoing and related ends, the one or moreaspects comprise the features hereinafter fully described andparticularly pointed out in the claims. The following description andthe annexed drawings set forth in detail certain illustrative featuresof the one or more aspects. These features are indicative, however, ofbut a few of the various ways in which the principles of various aspectsmay be employed, and this description is intended to include all suchaspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above-recited features of the presentdisclosure can be understood in detail, a more particular description,briefly summarized above, may be had by reference to aspects, some ofwhich are illustrated in the appended drawings. It is to be noted,however, that the appended drawings illustrate only certain typicalaspects of this disclosure and are therefore not to be consideredlimiting of its scope, for the description may admit to other equallyeffective aspects.

FIG. 1 is a block diagram conceptually illustrating an exampletelecommunications system, in accordance with certain aspects of thepresent disclosure.

FIG. 2 is a block diagram illustrating an example logical architectureof a distributed radio access network (RAN), in accordance with certainaspects of the present disclosure.

FIG. 3 is a diagram illustrating an example physical architecture of adistributed RAN, in accordance with certain aspects of the presentdisclosure.

FIG. 4 is a block diagram conceptually illustrating a design of anexample base station (BS) and user equipment (UE), in accordance withcertain aspects of the present disclosure.

FIG. 5 is a diagram showing examples for implementing a communicationprotocol stack, in accordance with certain aspects of the presentdisclosure.

FIG. 6 illustrates an example of a downlink-centric subframe, inaccordance with certain aspects of the present disclosure.

FIG. 7 illustrates an example of an uplink-centric subframe, inaccordance with certain aspects of the present disclosure.

FIG. 8 illustrates an example structure of a synchronization signalblock (SSB) broadcasted by a base station, in accordance with aspects ofthe present disclosure.

FIG. 9 illustrates example configurations of patterns of SSBtransmission opportunities based on various system parameters, inaccordance with aspects of the present disclosure.

FIG. 10 illustrates an example configuration of SSB transmissionopportunities with reference to frequency and time resources, inaccordance with certain aspects of the present disclosure.

FIG. 11 illustrates example wireless communications operations for useby a user equipment (UE), in accordance with certain aspects of thepresent disclosure.

FIG. 11A illustrates a wireless communications device that may includevarious components configured to perform operations for the techniquesdisclosed herein, such as one or more of the operations illustrated inFIG. 11.

FIGS. 12A-12C illustrate physical resource block (PRB) grids eachincluding a number of consecutive SSB PRBs and a number of consecutiveremaining minimum system information (RMSI) control resource set(CORESET) PRBs, in accordance with certain aspects of the presentdisclosure.

FIG. 13 illustrates an example table showing possible number offrequency offset values that a base station (BS) may indicate to a UE inthe indication in various scenarios, in accordance with certain aspectsof the present disclosure.

FIG. 14 illustrates an example table showing a fewer possible number offrequency offset values that a base station (BS) may indicate to a UE inthe indication in various scenarios, in accordance with certain aspectsof the present disclosure.

FIG. 15 shows three examples of RMSI CORESET being frequency divisionmultiplexed (FDM'd) with the SSB, in accordance with certain aspects ofthe present disclosure.

FIG. 16 illustrates an example table showing different offset valuesdepending on whether the RMSI subcarrier spacing (SCS) and the SSB SCSare the same or different, in accordance with certain aspects of thepresent disclosure.

FIG. 17 illustrates example wireless communications operations for useby a user equipment (UE), in accordance with certain aspects of thepresent disclosure.

FIG. 17A illustrates a wireless communications device that may includevarious components configured to perform operations for the techniquesdisclosed herein, such as one or more of the operations illustrated inFIG. 17.

FIG. 18 illustrates how a collection of FIGS. 18A-18D may be arranged toshow a complete figure including example mappings between the RMSItiming locations and the SSB timing locations for a frequency band below6 GHz.

FIGS. 18A-18D illustrate example mappings between the RMSI timinglocations and the SSB timing locations for a frequency band below 6 GHz,in accordance with certain aspects of the present disclosure.

FIG. 19 illustrates how a collection of FIGS. 19A-18B may be arranged toshow a complete figure including example mappings between the RMSItiming locations and the SSB timing locations for a frequency band above6 GHz.

FIGS. 19A-19B illustrate example mappings between the RMSI timinglocations and the SSB timing locations for a frequency band above 6 GHz,in accordance with certain aspects of the present disclosure.

FIG. 20 illustrates example wireless communications operations for useby a user equipment (UE), in accordance with certain aspects of thepresent disclosure.

FIG. 20A illustrates a wireless communications device that may includevarious components configured to perform operations for the techniquesdisclosed herein, such as one or more of the operations illustrated inFIG. 20.

FIG. 21 illustrates example wireless communications operations for useby a user equipment (UE), in accordance with certain aspects of thepresent disclosure.

FIG. 21A illustrates a wireless communications device that may includevarious components configured to perform operations for the techniquesdisclosed herein, such as one or more of the operations illustrated inFIG. 21.

FIG. 22 illustrates example wireless communications operations for useby a user equipment (UE), in accordance with certain aspects of thepresent disclosure.

FIG. 22A illustrates a wireless communications device that may includevarious components configured to perform operations for the techniquesdisclosed herein, such as one or more of the operations illustrated inFIG. 22.

To facilitate understanding, identical reference numerals have beenused, where possible, to designate identical elements that are common tothe figures. It is contemplated that elements disclosed in one aspectmay be beneficially utilized on other aspects without specificrecitation.

DETAILED DESCRIPTION

Aspects of the present disclosure relate to systems and methods fordetermining the locations of remaining minimum system information (RMSI)control resource set (CORESET) and other system information (OSI)CORESET in the time and frequency domains.

Aspects of the present disclosure provide apparatus, methods, processingsystems, and computer readable mediums for new radio (NR) (new radioaccess technology or 5G technology).

NR may support various wireless communication services, such as Enhancedmobile broadband (eMBB) targeting wide bandwidth (e.g. 80 MHz beyond),millimeter wave (mmW) targeting high carrier frequency (e.g. 27 GHz orbeyond), massive MTC (mMTC) targeting non-backward compatible MTCtechniques, and/or mission critical targeting ultra-reliable low latencycommunications (URLLC). These services may include latency andreliability requirements. These services may also have differenttransmission time intervals (TTI) to meet respective quality of service(QoS) requirements. In addition, these services may co-exist in the samesubframe.

In certain aspects, cell synchronization procedures may involve a basestation (e.g., BS 110 as described in relation to FIG. 1) broadcasting aset of signals in a SSB to facilitate cell search and synchronization bya UE (e.g., UE 120 as described in relation to FIG. 1). An SSB includesa primary synchronization signal (PSS), a secondary synchronizationsignal (SSS), and a physical broadcast channel (PBCH). An SSBtransmitted by a base station helps the UE determine system timinginformation such as a symbol timing based on the PSS, cellidentification based on the PSS and the SSS, and other parameters neededfor initial cell access based on system information sent in the PBCH.

The system information, in some cases, may include a minimum systeminformation (MSI) as well as other system information (OSI). In somecases, MSI includes information carried by the PBCH (similar to themaster information block (MIB) in LTE) as well as the remaining minimumsystem information (RMSI). The information carried by the PBCH (similarto MIB) is information that is used by the UE to acquire otherinformation from the cell. The RMSI includes information related to theUE's access to the cell as well as radio resource configuration commonfor all UEs in the cell. The RMSI may be interchangeably referred to assystem information block 1 (SIB1), the RMSI CORESET may beinterchangeably referred to as Type0-physical downlink control channel(PDCCH) common search space CORESET, the OSI CORESET may beinterchangeably referred to as Type0a-physical downlink control channel(PDCCH) common search space CORESET. The RMSI, as described above, iscarried by a physical downlink shared channel (PDSCH). UEs are scheduledto communicate using resources of the PDSCH based on information sent inthe PDCCH. The PDSCH may also carry the OSI.

The PDCCH (e.g., Type0-PDCCH), that schedules RMSI, may be transmittedin a control resource set (CORESET) within an RMSI PDCCH monitoringwindow associated with an SSB. In some cases, the RMSI CORESET(Type0-PDCH common search space CORESET) is a CORESET into which thePDCCH, for scheduling the PDSCH that carries the RMSI, is mapped.

Certain embodiments described herein are directed to enabling a wirelesscommunications device, such as a UE (e.g., UE 120), to determine thelocation of the RMSI CORESET and the OSI CORESET in the frequency andtime domains based on the location of the SSB transmissions in thefrequency and time domains. Determining the location of the RMSI CORESETand the OSI CORESET frequency and time resources enables the UE toreceive the RMSI CORESET and the OSI CORESET, respectively. By receivingthe RMSI CORESET, the UE is able to receive the PDCCH (e.g.,Type0-PDCCH) in the RMSI CORESET, based on which the UE is able toreceive and decode the PDSCH that carries RMSI. Also, the UE maydetermine the location of the OSI CORESET in the frequency and timedomains based on the location of the RMSI CORESET in the frequency andtime domains.

The following description provides examples, and is not limiting of thescope, applicability, or examples set forth in the claims. Changes maybe made in the function and arrangement of elements discussed withoutdeparting from the scope of the disclosure. Various examples may omit,substitute, or add various procedures or components as appropriate. Forinstance, the methods described may be performed in an order differentfrom that described, and various steps may be added, omitted, orcombined. Also, features described with respect to some examples may becombined in some other examples. For example, an apparatus may beimplemented or a method may be practiced using any number of the aspectsset forth herein. In addition, the scope of the disclosure is intendedto cover such an apparatus or method which is practiced using otherstructure, functionality, or structure and functionality in addition toor other than the various aspects of the disclosure set forth herein. Itshould be understood that any aspect of the disclosure disclosed hereinmay be embodied by one or more elements of a claim. The word “exemplary”is used herein to mean “serving as an example, instance, orillustration.” Any aspect described herein as “exemplary” is notnecessarily to be construed as preferred or advantageous over otheraspects.

The techniques described herein may be used for various wirelesscommunication networks such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA andother networks. The terms “network” and “system” are often usedinterchangeably. A CDMA network may implement a radio technology such asUniversal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includesWideband CDMA (WCDMA) and other variants of CDMA. cdma2000 coversIS-2000, IS-95 and IS-856 standards. A TDMA network may implement aradio technology such as Global System for Mobile Communications (GSM).An OFDMA network may implement a radio technology such as NR (e.g. 5GRA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11(Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA andE-UTRA are part of Universal Mobile Telecommunication System (UMTS). NRis an emerging wireless communications technology under development inconjunction with the 5G Technology Forum (5GTF). 3GPP Long TermEvolution (LTE) and LTE-Advanced (LTE-A) are releases of UMTS that useE-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described indocuments from an organization named “3rd Generation PartnershipProject” (3GPP). cdma2000 and UMB are described in documents from anorganization named “3rd Generation Partnership Project 2” (3GPP2). Thetechniques described herein may be used for the wireless networks andradio technologies mentioned above as well as other wireless networksand radio technologies. For clarity, while aspects may be describedherein using terminology commonly associated with 3G and/or 4G wirelesstechnologies, aspects of the present disclosure can be applied in othergeneration-based communication systems, such as 5G and later, includingNR technologies.

Example Wireless Communications System

FIG. 1 illustrates an example wireless network 100 in which aspects ofthe present disclosure may be performed. For example, user equipment 120may receive a remaining minimum system information (RMSI) controlresource set (CORESET) configuration in a physical broadcast channel(PBCH) from base station 120. The RMSI CORESET configuration may includean indication that UE 120 may use to determine the locations of the RMSICORESET frequency resources. In addition, UE 120 may store a mapping ofSSB time resources to RMSI CORESET time resources that enables UE 120 todetermine locations of RMSI CORESET time resources.

The UE may also determine the time and frequency locations of othersystem information (OSI) CORESET based on the time and frequencylocations of the RMSI CORESET.

As illustrated in FIG. 1, the wireless network 100 may include a numberof BSs 110 and other network entities. A BS may be a station thatcommunicates with UEs. Each BS 110 may provide communication coveragefor a particular geographic area. In 3GPP, the term “cell” can refer toa coverage area of a Node B (NB) and/or a Node B subsystem serving thiscoverage area, depending on the context in which the term is used. In NRsystems, the term “cell”, BS, Next Generation Node B (gNB), Node B, 5GNB, access point (AP), NR BS, NR BS, or transmission reception (TRP) maybe interchangeable. In some examples, a cell may not necessarily bestationary, and the geographic area of the cell may move according tothe location of a mobile BS. In some examples, the BSs may beinterconnected to one another and/or to one or more other BSs or networknodes (not shown) in the wireless network 100 through various types ofbackhaul interfaces such as a direct physical connection, a virtualnetwork, or the like using any suitable transport network.

In general, any number of wireless networks may be deployed in a givengeographic area. Each wireless network may support a particular radioaccess technology (RAT) and may operate on one or more frequencies. ARAT may also be referred to as a radio technology, an air interface,etc. A frequency may also be referred to as a carrier, a frequencychannel, a tone, a subband, a subcarrier, etc. Each frequency maysupport a single RAT in a given geographic area in order to avoidinterference between wireless networks of different RATs. In some cases,NR or 5G RAT networks may be deployed.

A BS may provide communication coverage for a macro cell, a pico cell, afemto cell, and/or other types of cell. A macro cell may cover arelatively large geographic area (e.g., several kilometers in radius)and may allow unrestricted access by UEs with service subscription. Apico cell may cover a relatively small geographic area and may allowunrestricted access by UEs with service subscription. A femto cell maycover a relatively small geographic area (e.g., a home) and may allowrestricted access by UEs having association with the femto cell (e.g.,UEs in a Closed Subscriber Group (CSG), UEs for users in the home,etc.). A BS for a macro cell may be referred to as a macro BS. A BS fora pico cell may be referred to as a pico BS. A BS for a femto cell maybe referred to as a femto BS or a home BS. In the example shown in FIG.1, the BSs 110 a, 110 b and 110 c may be macro BSs for the macro cells102 a, 102 b and 102 c, respectively. The BS 110 x may be a pico BS fora pico cell 102 x. The BSs 110 y and 110 z may be femto BS for the femtocells 102 y and 102 z, respectively. A BS may support one or multiple(e.g., three) cells.

The wireless network 100 may also include relay stations. A relaystation is a station that receives a transmission of data and/or otherinformation from an upstream station (e.g., a BS or a UE) and sends atransmission of the data and/or other information to a downstreamstation (e.g., a UE or a BS). A relay station may also be a UE thatrelays transmissions for other UEs. In the example shown in FIG. 1, arelay station 110 r may communicate with the BS 110 a and a UE 120 r inorder to facilitate communication between the BS 110 a and the UE 120 r.A relay station may also be referred to as a relay BS, a relay, etc.

The wireless network 100 may be a heterogeneous network that includesBSs of different types, e.g., macro BS, pico BS, femto BS, relays, etc.These different types of BSs may have different transmit power levels,different coverage areas, and different impact on interference in thewireless network 100. For example, macro BS may have a high transmitpower level (e.g., 20 Watts) whereas pico BS, femto BS, and relays mayhave a lower transmit power level (e.g., 1 Watt).

The wireless network 100 may support synchronous or asynchronousoperation. For synchronous operation, the BSs may have similar frametiming, and transmissions from different BSs may be approximatelyaligned in time. For asynchronous operation, the BSs may have differentframe timing, and transmissions from different BSs may not be aligned intime. The techniques described herein may be used for both synchronousand asynchronous operation.

A network controller 130 may couple to a set of BSs and providecoordination and control for these BSs. The network controller 130 maycommunicate with the BSs 110 via a backhaul. The BSs 110 may alsocommunicate with one another, e.g., directly or indirectly via wirelessor wireline backhaul.

The UEs 120 (e.g., 120 x, 120 y, etc.) may be dispersed throughout thewireless network 100, and each UE may be stationary or mobile. A UE mayalso be referred to as a mobile station, a terminal, an access terminal,a subscriber unit, a station, a Customer Premises Equipment (CPE), acellular phone, a smart phone, a personal digital assistant (PDA), awireless modem, a wireless communication device, a handheld device, alaptop computer, a cordless phone, a wireless local loop (WLL) station,a tablet, a camera, a gaming device, a netbook, a smartbook, anultrabook, a medical device or medical equipment, a biometricsensor/device, a wearable device such as a smart watch, smart clothing,smart glasses, a smart wrist band, smart jewelry (e.g., a smart ring, asmart bracelet, etc.), an entertainment device (e.g., a music device, avideo device, a satellite radio, etc.), a vehicular component or sensor,a smart meter/sensor, industrial manufacturing equipment, a globalpositioning system device, or any other suitable device that isconfigured to communicate via a wireless or wired medium. Some UEs maybe considered evolved or machine-type communication (MTC) devices orevolved MTC (eMTC) devices. MTC and eMTC UEs include, for example,robots, drones, remote devices, sensors, meters, monitors, locationtags, etc., that may communicate with a BS, another device (e.g., remotedevice), or some other entity. A wireless node may provide, for example,connectivity for or to a network (e.g., a wide area network such asInternet or a cellular network) via a wired or wireless communicationlink. Some UEs may be considered Internet-of-Things (IoT) devices ornarrowband IoT (NB-IoT) devices.

In FIG. 1, a solid line with double arrows indicates desiredtransmissions between a UE and a serving BS, which is a BS designated toserve the UE on the downlink and/or uplink. A dashed line with doublearrows indicates interfering transmissions between a UE and a BS.

Certain wireless networks (e.g., LTE) utilize orthogonal frequencydivision multiplexing (OFDM) on the downlink and single-carrierfrequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDMpartition the system bandwidth into multiple (K) orthogonal subcarriers,which are also commonly referred to as tones, bins, etc. Each subcarriermay be modulated with data. In general, modulation symbols are sent inthe frequency domain with OFDM and in the time domain with SC-FDM. Thespacing between adjacent subcarriers may be fixed, and the total numberof subcarriers (K) may be dependent on the system bandwidth. Forexample, the spacing of the subcarriers may be 15 kHz and the minimumresource allocation (called a physical resource block (PRB)) may be 12subcarriers (or 180 kHz). Consequently, the nominal FFT size may beequal to 128, 256, 512, 1024 or 2048 for system bandwidth of 1.25, 2.5,5, 10 or 20 megahertz (MHz), respectively. The system bandwidth may alsobe partitioned into subbands. For example, a subband may cover 1.08 MHz(i.e., 6 PRBs), and there may be 1, 2, 4, 8 or 16 subbands for systembandwidth of 1.25, 2.5, 5, 10 or 20 MHz, respectively.

While aspects of the examples described herein may be associated withLTE technologies, aspects of the present disclosure may be applicablewith other wireless communications systems, such as NR.

NR may utilize OFDM with a CP on the uplink and downlink and includesupport for half-duplex operation using TDD. A single component carrierbandwidth of 100 MHz may be supported. NR resource blocks may span 12subcarriers with a subcarrier bandwidth of 75 kHz over a 0.1 msduration. Each radio frame may consist of two half frames, each halfframe consisting of 5 subframes, with a length of 10 ms. Consequently,each subframe may have a length of 1 ms. Each subframe may indicate alink direction (i.e., DL or UL) for data transmission and the linkdirection for each subframe may be dynamically switched. Each subframemay include DL/UL data as well as DL/UL control data. UL and DLsubframes for NR may be as described in more detail below with respectto FIGS. 6 and 7. Beamforming may be supported and beam direction may bedynamically configured. MIMO transmissions with precoding may also besupported. MIMO configurations in the DL may support up to 8 transmitantennas with multi-layer DL transmissions up to 8 streams and up to 2streams per UE. Multi-layer transmissions with up to 2 streams per UEmay be supported. Aggregation of multiple cells may be supported with upto 8 serving cells. Alternatively, NR may support a different airinterface, other than an OFDM-based. NR networks may include entitiessuch CUs and/or DUs.

In LTE, the basic transmission time interval (TTI) or packet duration isthe 1 subframe. In NR, a subframe is still 1 ms, but the basic TTI isreferred to as a slot. A subframe contains a variable number of slots(e.g., 1, 2, 4, 8, 16, . . . slots) depending on the tone-spacing (e.g.,15, 30, 60, 120, 240 . . . kHz).

Beamforming generally refers to the use of multiple antennas to controlthe direction of a wavefront by appropriately weighting the magnitudeand phase of individual antenna signals (for transmit beamforming).Beamforming may result in enhanced coverage, as each antenna in thearray may make a contribution to the steered signal, an array gain (orbeamforming gain) is achieved. Receive beamforming makes it possible todetermine the direction that the wavefront will arrive (direction ofarrival, or DoA). It may also be possible to suppress selectedinterfering signals by applying a beam pattern null in the direction ofthe interfering signal. Adaptive beamforming refers to the technique ofcontinually applying beamforming to a moving receiver.

In some examples, access to the air interface may be scheduled, whereina scheduling entity (e.g., a BS) allocates resources for communicationamong some or all devices and equipment within its service area or cell.Within the present disclosure, as discussed further below, thescheduling entity may be responsible for scheduling, assigning,reconfiguring, and releasing resources for one or more subordinateentities. That is, for scheduled communication, subordinate entitiesutilize resources allocated by the scheduling entity. BSs are not theonly entities that may function as a scheduling entity. That is, in someexamples, a UE may function as a scheduling entity, scheduling resourcesfor one or more subordinate entities (e.g., one or more other UEs). Inthis example, the UE is functioning as a scheduling entity, and otherUEs utilize resources scheduled by the UE for wireless communication. AUE may function as a scheduling entity in a peer-to-peer (P2P) network,and/or in a mesh network. In a mesh network example, UEs may communicatedirectly with one another in addition to communicating with thescheduling entity.

Thus, in a wireless communication network with a scheduled access totime-frequency resources and having a cellular configuration, a P2Pconfiguration, and a mesh configuration, a scheduling entity and one ormore subordinate entities may communicate utilizing the scheduledresources.

FIG. 2 illustrates an example logical architecture of a distributedradio access network (RAN) 200, which may be implemented in the wirelesscommunication system illustrated in FIG. 1. A 5G access node 206 mayinclude an access node controller (ANC) 202. The ANC 202 may be acentral unit (CU) of the distributed RAN 200. The backhaul interface tothe next generation core network (NG-CN) 204 may terminate at the ANC202. The backhaul interface to neighboring next generation access nodes(NG-ANs) 210 may terminate at the ANC 202. The ANC 202 may include oneor more TRPs 208 (which may also be referred to as BSs, NR BSs, Node Bs,gNBs, 5G NBs, APs, or some other term). As described above, a TRP may beused interchangeably with “cell.”

The TRPs 208 may be a DU. The TRPs 208 may be connected to one ANC (ANC202) or more than one ANC (not illustrated). For example, for RANsharing, radio as a service (RaaS), and service specific ANDdeployments, the TRP may be connected to more than one ANC. A TRP mayinclude one or more antenna ports. The TRPs may be configured toindividually (e.g., dynamic selection) or jointly (e.g., jointtransmission) serve traffic to a UE.

The logical architecture may support fronthauling solutions acrossdifferent deployment types. For example, the logical architecture may bebased on transmit network capabilities (e.g., bandwidth, latency, and/orjitter). The logical architecture may share features and/or componentswith LTE. The NG-AN 210 may support dual connectivity with NR. The NG-AN210 may share a common fronthaul for LTE and NR.

The logical architecture may enable cooperation between and among TRPs208. For example, cooperation may be preset within a TRP and/or acrossTRPs via the ANC 202. An inter-TRP interface may not be used.

The logical architecture may support a dynamic configuration of splitlogical functions. As will be described in more detail with reference toFIG. 5, the Radio Resource Control (RRC) layer, Packet Data ConvergenceProtocol (PDCP) layer, Radio Link Control (RLC) layer, Medium AccessControl (MAC) layer, and a Physical (PHY) layers may be adaptably placedat the DU or CU (e.g., TRP or ANC, respectively). A BS may include acentral unit (CU) (e.g., ANC 202) and/or one or more distributed units(e.g., one or more TRPs 208).

FIG. 3 illustrates an example physical architecture of a distributed RAN300, according to aspects of the present disclosure. A centralized corenetwork unit (C-CU) 302 may host core network functions. The C-CU 302may be centrally deployed. C-CU functionality may be offloaded (e.g., toadvanced wireless services (AWS)), in an effort to handle peak capacity.

A centralized RAN unit (C-RU) 304 may host one or more ANC functions.The C-RU 304 may host core network functions locally. The C-RU 304 mayhave distributed deployment. The C-RU 304 may be close to the networkedge.

A DU 306 may host one or more TRPs (edge node (EN), an edge unit (EU), aradio head (RH), a smart radio head (SRH), or the like). The DU 306 maybe located at edges of the network with radio frequency (RF)functionality.

FIG. 4 illustrates example components of the BS 110 and UE 120illustrated in FIG. 1, which may be used to implement aspects of thepresent disclosure.

As described above, the BS 110 may be a gNB, TRP, etc. One or morecomponents of the BS 110 and UE 120 may be used to practice aspects ofthe present disclosure. For example, antennas 452, Tx/Rx 222, processors466, 458, 464, and/or controller/processor 480 of the UE 120 and/orantennas 434, processors 460, 420, 438, and/or controller/processor 440of the BS 110 may be used to perform the operations described herein andillustrated with reference to FIGS. 11, 17, and 20.

FIG. 4 shows a block diagram of a design of a BS 110 and a UE 120, whichmay be one of the BSs and one of the UEs in FIG. 1. For a restrictedassociation scenario, the BS 110 may be the macro BS 110 c in FIG. 1,and the UE 120 may be the UE 120 y. The BS 110 may also be a BS of someother type. The BS 110 may be equipped with antennas 434 a through 434t, and the UE 120 may be equipped with antennas 452 a through 452 r.

At the BS 110, a transmit processor 420 may receive data from a datasource 412 and control information from a controller/processor 440. Thecontrol information may be for the Physical Broadcast Channel (PBCH),Physical Control Format Indicator Channel (PCFICH), Physical Hybrid ARQIndicator Channel (PHICH), Physical Downlink Control Channel (PDCCH),etc. The data may be for the Physical Downlink Shared Channel (PDSCH),etc. The processor 420 may process (e.g., encode and symbol map) thedata and control information to obtain data symbols and control symbols,respectively. The processor 420 may also generate reference symbols,e.g., for a primary synchronization signal (PSS), primarysynchronization signal (SSS), and cell-specific reference signal. Atransmit (TX) multiple-input multiple-output (MIMO) processor 430 mayperform spatial processing (e.g., precoding) on the data symbols, thecontrol symbols, and/or the reference symbols, if applicable, and mayprovide output symbol streams to the modulators (MODs) 432 a through 432t. Each modulator 432 may process a respective output symbol stream(e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator432 may further process (e.g., convert to analog, amplify, filter, andupconvert) the output sample stream to obtain a downlink signal.Downlink signals from modulators 432 a through 432 t may be transmittedvia the antennas 434 a through 434 t, respectively. As described in moredetail below, in some cases, synchronization, reference signals, andbroadcast signals may have a flexible bandwidth allocation and may notbe centered around the DC tone.

At the UE 120, the antennas 452 a through 452 r may receive the downlinksignals from the base station 110 and may provide received signals tothe demodulators (DEMODs) 454 a through 454 r, respectively. Eachdemodulator 454 may condition (e.g., filter, amplify, downconvert, anddigitize) a respective received signal to obtain input samples. Eachdemodulator 454 may further process the input samples (e.g., for OFDM,etc.) to obtain received symbols. A MIMO detector 456 may obtainreceived symbols from all the demodulators 454 a through 454 r, performMIMO detection on the received symbols if applicable, and providedetected symbols. A receive processor 458 may process (e.g., demodulate,deinterleave, and decode) the detected symbols, provide decoded data forthe UE 120 to a data sink 460, and provide decoded control informationto a controller/processor 480.

On the uplink, at the UE 120, a transmit processor 464 may receive andprocess data (e.g., for the Physical Uplink Shared Channel (PUSCH)) froma data source 462 and control information (e.g., for the Physical UplinkControl Channel (PUCCH) from the controller/processor 480. The transmitprocessor 464 may also generate reference symbols for a referencesignal. The symbols from the transmit processor 464 may be precoded by aTX MIMO processor 466 if applicable, further processed by thedemodulators 454 a through 454 r (e.g., for SC-FDM, etc.), andtransmitted to the BS 110. At the BS 110, the uplink signals from the UE120 may be received by the antennas 434, processed by the modulators432, detected by a MIMO detector 436 if applicable, and furtherprocessed by a receive processor 438 to obtain decoded data and controlinformation sent by the UE 120. The receive processor 438 may providethe decoded data to a data sink 439 and the decoded control informationto the controller/processor 440.

The controllers/processors 440 and 480 may direct the operation at theBS 110 and the UE 120, respectively. The processor 440 and/or otherprocessors and modules at the BS 110 may perform or direct the executionprocesses for the techniques described herein. The processor 480 and/orother processors and modules at the UE 120 may also perform or direct,e.g., the execution of the functional blocks illustrated in FIGS. 11,17, and 20, and/or other processes for the techniques described herein.The memories 442 and 482 may store data and program codes for the BS 110and the UE 120, respectively. A scheduler 444 may schedule UEs for datatransmission on the downlink and/or uplink.

FIG. 5 illustrates a diagram 500 showing examples for implementing acommunications protocol stack, according to aspects of the presentdisclosure. The illustrated communications protocol stacks may beimplemented by devices operating in a in a 5G system (e.g., a systemthat supports uplink-based mobility). Diagram 500 illustrates acommunications protocol stack including a Radio Resource Control (RRC)layer 510, a Packet Data Convergence Protocol (PDCP) layer 515, a RadioLink Control (RLC) layer 520, a Medium Access Control (MAC) layer 525,and a Physical (PHY) layer 530. In various examples the layers of aprotocol stack may be implemented as separate modules of software,portions of a processor or ASIC, portions of non-collocated devicesconnected by a communications link, or various combinations thereof.Collocated and non-collocated implementations may be used, for example,in a protocol stack for a network access device (e.g., ANs, CUs, and/orDUs) or a UE.

A first option 505-a shows a split implementation of a protocol stack,in which implementation of the protocol stack is split between acentralized network access device (e.g., an ANC 202 in FIG. 2) anddistributed network access device (e.g., DU 208 in FIG. 2). In the firstoption 505-a, an RRC layer 510 and a PDCP layer 515 may be implementedby the central unit, and an RLC layer 520, a MAC layer 525, and a PHYlayer 530 may be implemented by the DU. In various examples the CU andthe DU may be collocated or non-collocated. The first option 505-a maybe useful in a macro cell, micro cell, or pico cell deployment.

A second option 505-b shows a unified implementation of a protocolstack, in which the protocol stack is implemented in a single networkaccess device (e.g., access node (AN), new radio base station (NR BS), anew radio Node-B (NR NB), a network node (NN), or the like.). In thesecond option, the RRC layer 510, the PDCP layer 515, the RLC layer 520,the MAC layer 525, and the PHY layer 530 may each be implemented by theAN. The second option 505-b may be useful in a femto cell deployment.

Regardless of whether a network access device implements part or all ofa protocol stack, a UE may implement an entire protocol stack (e.g., theRRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525,and the PHY layer 530).

FIG. 6 is a diagram showing an example format of a DL-centric subframe600. The DL-centric subframe 600 may include a control portion 602. Thecontrol portion 602 may exist in the initial or beginning portion of theDL-centric subframe 600. The control portion 602 may include variousscheduling information and/or control information corresponding tovarious portions of the DL-centric subframe 600. In some configurations,the control portion 602 may be a physical DL control channel (PDCCH), asindicated in FIG. 6. The DL-centric subframe 600 may also include a DLdata portion 604. The DL data portion 604 may sometimes be referred toas the payload of the DL-centric subframe 600. The DL data portion 604may include the communication resources utilized to communicate DL datafrom the scheduling entity (e.g., UE or BS) to the subordinate entity(e.g., UE). In some configurations, the DL data portion 604 may be aphysical DL shared channel (PDSCH).

The DL-centric subframe 600 may also include a common UL portion 606.The common UL portion 606 may be referred to as an UL burst, a common ULburst, and/or various other suitable terms. The common UL portion 606may include feedback information corresponding to various other portionsof the DL-centric subframe 600. For example, the common UL portion 606may include feedback information corresponding to the control portion602. Non-limiting examples of feedback information may include an ACKsignal, a NACK signal, a HARQ indicator, and/or various other suitabletypes of information. The common UL portion 606 may include additionalor alternative information, such as information pertaining to randomaccess channel (RACH) procedures, scheduling requests (SRs), and variousother suitable types of information. As illustrated in FIG. 6, the endof the DL data portion 604 may be separated in time from the beginningof the common UL portion 606. This time separation may be referred to asa gap, a guard period, a guard interval, and/or various other suitableterms. This separation provides time for the switch-over from DLcommunication (e.g., reception operation by the subordinate entity(e.g., UE)) to UL communication (e.g., transmission by the subordinateentity (e.g., UE)). One of ordinary skill in the art will understandthat the foregoing is merely one example of a DL-centric subframe andalternative structures having similar features may exist withoutnecessarily deviating from the aspects described herein.

FIG. 7 is a diagram showing an example format of an UL-centric subframe700. The UL-centric subframe 700 may include a control portion 702. Thecontrol portion 702 may exist in the initial or beginning portion of theUL-centric subframe 700. The control portion 702 in FIG. 7 may besimilar to the control portion 602 described above with reference toFIG. 6. The UL-centric subframe 700 may also include an UL data portion704. The UL data portion 704 may be referred to as the payload of theUL-centric subframe 700. The UL portion may refer to the communicationresources utilized to communicate UL data from the subordinate entity(e.g., UE) to the scheduling entity (e.g., UE or BS). In someconfigurations, the control portion 702 may be a PDCCH.

As illustrated in FIG. 7, the end of the control portion 702 may beseparated in time from the beginning of the UL data portion 704. Thistime separation may be referred to as a gap, guard period, guardinterval, and/or various other suitable terms. This separation providestime for the switch-over from DL communication (e.g., receptionoperation by the scheduling entity) to UL communication (e.g.,transmission by the scheduling entity). The UL-centric subframe 700 mayalso include a common UL portion 706. The common UL portion 706 in FIG.7 may be similar to the common UL portion 606 described above withreference to FIG. 6. The common UL portion 706 may additional oralternative include information pertaining to channel quality indicator(CQI), sounding reference signals (SRSs), and various other suitabletypes of information. One of ordinary skill in the art will understandthat the foregoing is merely one example of an UL-centric subframe andalternative structures having similar features may exist withoutnecessarily deviating from the aspects described herein.

In one example, a frame may include both UL centric subframes and DLcentric subframes. In this example, the ratio of UL centric subframes toDL subframes in a frame may be dynamically adjusted based on the amountof UL data and the amount of DL data that are transmitted. For example,if there is more UL data, then the ratio of UL centric subframes to DLsubframes may be increased. Conversely, if there is more DL data, thenthe ratio of UL centric subframes to DL subframes may be decreased.

In some circumstances, two or more subordinate entities (e.g., UEs) maycommunicate with each other using sidelink signals. Real-worldapplications of such sidelink communications may include public safety,proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V)communications, Internet of Everything (IoE) communications, IoTcommunications, mission-critical mesh, and/or various other suitableapplications. Generally, a sidelink signal may refer to a signalcommunicated from one subordinate entity (e.g., UE1) to anothersubordinate entity (e.g., UE2) without relaying that communicationthrough the scheduling entity (e.g., UE or BS), even though thescheduling entity may be utilized for scheduling and/or controlpurposes. In some examples, the sidelink signals may be communicatedusing a licensed spectrum (unlike wireless local area networks, whichtypically use an unlicensed spectrum).

A UE may operate in various radio resource configurations, including aconfiguration associated with transmitting pilots using a dedicated setof resources (e.g., a radio resource control (RRC) dedicated state,etc.) or a configuration associated with transmitting pilots using acommon set of resources (e.g., an RRC common state, etc.). Whenoperating in the RRC dedicated state, the UE may select a dedicated setof resources for transmitting a pilot signal to a network. Whenoperating in the RRC common state, the UE may select a common set ofresources for transmitting a pilot signal to the network. In eithercase, a pilot signal transmitted by the UE may be received by one ormore network access devices, such as an AN, or a DU, or portionsthereof. Each receiving network access device may be configured toreceive and measure pilot signals transmitted on the common set ofresources, and also receive and measure pilot signals transmitted ondedicated sets of resources allocated to the UEs for which the networkaccess device is a member of a monitoring set of network access devicesfor the UE. One or more of the receiving network access devices, or a CUto which receiving network access device(s) transmit the measurements ofthe pilot signals, may use the measurements to identify serving cellsfor the UEs, or to initiate a change of serving cell for one or more ofthe UEs.

Example Synchronization Signal Block Design

In certain aspects, cell synchronization procedures may involve a basestation (e.g., BS 110) broadcasting a set of signals in an SSB tofacilitate cell search and synchronization by UEs (e.g., UEs 120).

FIG. 8 illustrates an example of the structure of a SSB 800 broadcastedby a BS (e.g., BS 110). The configuration of SSB 800 includes a PSS 810,a SSS 820, and PBCH 830 multiplexed between the PSS 810 and SSS 820 asshown in FIG. 8. The PBCH 830 may include reference signals such asdemodulation reference signals (DMRS) signals. Accordingly, each SSB 800transmitted by BS 110 may help the UE 120 determine system timinginformation such as a symbol timing based on PSS 810, cellidentification based on PSS 810 and SSS 820, and other parameters neededfor initial cell access based on a Master Information Block (MIB) sentin the PBCH 830.

In some implementations, the PSS 810 and SSS 820 each occupy one symbolin the time domain, while the PBCH 830 occupies two symbols but is splitinto two parts with a first half in one symbol between the PSS 810 andSSS 820, and a second half in a second symbol after SSS 820, as seen inFIG. 8. In the frequency domain, the PSS 810 and SSS 820 may each occupy127 resource elements or subcarriers, while the PBCH 830 may occupy 288resource elements. In some embodiments, a resource element refers to onesymbol in one subcarrier of a resource block. For example, when aresource block comprises 12 subcarriers and 7 symbols, the resourceblock may comprise 84 (12 subcarriers*7 symbols) resource elements incase of a normal cyclic prefix (72 for extended CP). The frequencylocation of the SSB 800 may not necessarily be in the center 6 resourceblocks of the frequency band but may vary depending on the sync rasterand may be a function of channel raster parameters.

Base station 110 may periodically transmit an SSB 800 to allow UEs 120the opportunity to synchronize with the system. In certain aspects, thebase station 110 may transmit multiple instances of SSBs in asynchronization signal burst (SS burst), instead of, for example, onlyone instance of PSS and SSS every 5 ms. In a SS burst, multiple SSBtransmissions may be sent within a 5 ms time window. The multiple SSBtransmissions may allow for coverage enhancements and/or directionalbeams to UEs in different locations. For example, the BS may transmitSSBs using different transmit beams that are spatially directed todifferent locations, thereby, allowing UEs in each of those differentlocations to receive the SSBs. BS 110, however, may be limited bypredefined rules with respect to the number of SSBs that can betransmitted within a particular time frame. The limitations may be basedon various factors, including the particular subcarrier spacing used bythe system and the frequency band in which the system operates.

FIG. 9 illustrates example configurations 900 of patterns of SSBstransmission opportunities based on various system parameters. As shownin FIG. 9, the number of SSB transmission opportunities for a BS 110 andthe corresponding locations of the SSB transmission opportunities withina measurement window (e.g., 5 ms window) may depend on the subcarrierspacing employed by the BS and the frequency band in which the BSoperates. The UE may measure cell discovery reference signal (DRS)according to periodically configured DRS measurement timingconfiguration (DMTC) period windows.

The DMTC may be configured for measurements of a serving cell orneighbor cells, or both. Further, the DMTC may be frequency specific ormay be applicable to multiple frequencies in various examples. Thelength of a slot in each configuration may vary depending on thesubcarrier spacing used in the configuration. In configuration 910, asubcarrier spacing of 120 kHz is used within an over-6 GHz frequencyband (e.g., 60 GHz frequency band). Within a 5 ms window, the basestation 110 in this configuration 910 may be allowed to transmit L=64SSB s (i.e., two SSB s per slot), which may be required to betransmitted according to a particular pattern of allocated resources forthe SSB s.

In configuration 920, a subcarrier spacing of 240 kHz is used within afrequency band of over 6 GHz (e.g., 60 GHz), and the maximum number ofSSB transmissions is L=64, which may be required to be transmittedaccording to a particular pattern of allocated resources for the SSB s.The 64 SSB s may be referred to as an SS burst set. The pattern andmaximum number of SSB s allowed within a measurement window may vary inother configurations, depending on the subcarrier spacing used andfrequency band in which the base station 110 and UE 120 operate.

FIG. 10 illustrates an example configuration 1000 of SSB transmissionopportunities with reference to frequency and time resources (e.g.,symbols). For simplicity, FIG. 10 illustrates three SSB transmissionopportunities, but the number of SSB transmission opportunities within aSS burst set may be more, such as L=64 SS blocks in a SS burst set foroperation in over 6 GHz frequency bands (for carrier frequencies below 3GHz, L may be 4, and for carrier frequencies between 3 and 6 GHz, L maybe 8). In some instances, there may be predefined locations within ameasurement window that are allocated for SSB transmissions. Forexample, resources corresponding to SSB transmission opportunities 1010,1020, and 1030 may be allocated to transmitting SSBs, and a base stationmay choose to transmit in all, none, or any combination of SSBtransmission opportunities 1010, 1020, or 1030.

The base station 110 may choose to transmit SSBs in SSB transmissionopportunities 1010 and 1030 while refraining from transmitting in SSBtransmission opportunity 1020. In this scenario, the base station 110transmits SSBs in SSB transmission opportunities 1010 and 1030 in amanner that is not “logically consecutive,” that is, there may beintervening SSB transmission opportunities (e.g., corresponding to SSBtransmission opportunity 1020) between SSB transmission opportunities(1010 and 1030) in which the base station 110 does not transmit an SSB.Alternatively, the base station 110 may instead transmit SSBs in SSBtransmission opportunities 1010 and 1020, in which case, the transmittedSSBs are considered logically consecutive.

As described above, for initial access to a cell, the UE may obtainsystem information. The system information, in some cases, may include aminimum system information (MSI) as well as other system information(OSI). Using the MSI, the UE is able to perform a random access channel(RACH) procedure with the cell. In some cases, MSI includes informationcarried by the PBCH (similar to the master information block (MIB) inLTE) as well as the remaining minimum system information (RMSI). Theinformation carried by the PBCH (similar to MIB) is information that isused by the UE to acquire other information from the cell (BS). The RMSIincludes information related to the UE's access to the cell (BS) as wellas radio resource configuration common for all UEs in the cell. The RMSImay be interchangeably referred to as system information block 1 (SIB1),the RMSI CORESET may be interchangeably referred to as Type0-physicaldownlink control channel (PDCCH) common search space CORESET (i.e.,CORESET configuration for Type0-physical downlink control channel(PDCCH) common search space), the OSI CORESET may be interchangeablyreferred to as Type0a-physical downlink control channel (PDCCH) commonsearch space CORESET. The RMSI, as described above, is carried by aphysical downlink shared channel (PDSCH). UEs are scheduled tocommunicate using resources of the PDSCH based on information sent inthe PDCCH. The PDSCH may also carry the OSI.

The PDCCH resources, that schedule the RMSI, may be transmitted by a BSin a control resource set (CORESET) within an RMSI PDCCH monitoringwindow associated with the SSB. In other words, the PDCCH is mapped intothe CORESET. The RMSI PDCCH monitoring window has an offset, a duration(e.g., length), and a periodicity.

A CORESET may be defined with respect to the frequency domain and thetime domain. In the frequency domain, the CORESET is defined by thenumber of resource blocks (PRBs) (e.g., 24 PRBs, 48 PRBs), which may bereferred to as the CORESET bandwidth (e.g., multiple of 6 PRBs). In somecases, the PRBs may be contiguous or non-contiguous. In the time domain,the CORESET is defined by the number of OFDM symbols. A symbol refers toa time resource. For example, the downlink control region in the timeslot may have up to 3 OFDM symbols. In some embodiments, the CORESET maybe a one-symbol CORESET, a two-symbol CORESET, or a three-symbolCORESET.

In some cases, the RMSI CORESET is a CORESET into which the PDCCHresources, for scheduling the PDSCH that carries RMSI, are mapped. Insome cases, the RMSI CORESET configuration may be signaled in the PBCH,which is carried by a SSB. The RMSI CORESET configuration may includeinformation relating to the RMSI CORESET bandwidth (BW) (e.g., thenumber of RMSI CORESET PRBs in the RMSI CORESET may be referred to asthe RMSI CORESET bandwidth (BW)), the RMSI frequency offset value, andthe OFDM symbols. In some cases, the OSI CORESET is a CORESET into whichthe PDCCH resources, for scheduling the PDSCH that carries OSI, aremapped.

Certain embodiments described herein are directed to enabling a wirelesscommunications device, such as a UE, to determine the location of theRMSI CORESET and the OSI CORESET in the frequency and time domains. Byreceiving the RMSI CORESET, the UE is able to receive the PDCCH(Type0-PDCCH) in the RMSI (Type0-PDCCH common search space) CORESET,based on which the UE is able to receive and decode the PDSCH thatcarries RMSI. Also, the UE may determine the location of the OSI CORESETin the frequency and time domains based on the location of the RMSICORESET in the frequency and time domains.

Note that the locations of the RMSI CORESET in the frequency and timedomains may be interchangeably referred to herein as the frequencylocation and time location of the RMSI CORESET, respectively. Also, thelocations of the OSI CORESET in the frequency and time domains may beinterchangeably referred to herein as the frequency location and timelocation of the OSI CORESET, respectively.

Example RMSI Offset Design

In some embodiments, determining the location of the RMSI CORESET in thefrequency and time domains may be based on the location of the SSBtransmission in the frequency and time domains.

FIG. 11 is a flow diagram illustrating example operations 1100 forwireless communications. Operations 1100 may be performed, for example,by a UE (e.g., UE 120), for determining the location of the RMSI CORESETin the frequency domain. Operations 1100 begin at, 1102, by receiving aType0-physical downlink control channel (PDCCH) common search spacecontrol resource set (CORESET) configuration and a physical resourceblock (PRB) grid offset in a physical broadcast channel (PBCH) carriedby a synchronization signal block (SSB), the Type0-PDCCH common searchspace CORESET configuration comprising an indication indicative of oneor more offset values corresponding to one or more offsets relating tofrequency locations of Type0-PDCCH common search space CORESET resourceblocks (PRBs) relative to frequency locations of PRBs of the SSB. At1104, operations 1100 continue by aligning a PRB grid of SSB with a PRBgrid of Type0-PDCCH common search space CORESET by applying the PRB gridoffset. At 1106, operations 1100 continue by mapping the indication tothe one or more offset values using a mapping stored by the UE. At 1108,operations 1100 continue by determining the frequency locations of theType0-PDCCH common search space CORESET PRBs based on the one or moreoffset values and the frequency locations of the SSB PRBs. At 1110,operations 1100 continue by receiving Type0-PDCCH in the Type0-PDCCHcommon search space CORESET.

FIG. 11A illustrates a wireless communications device 1100A that mayinclude various components (e.g., corresponding to means-plus-functioncomponents) configured to perform operations for the techniquesdisclosed herein, such as one or more of the operations illustrated inFIG. 11. The communications device 1100A includes a processing system1114 coupled to a transceiver 1112. The transceiver 1112 is configuredto transmit and receive signals for the communications device 1100A viaan antenna 1113. The processing system 1114 may be configured to performprocessing functions for the communications device 1100A, such asprocessing signals, etc.

The processing system 1114 includes a processor 1109 coupled to acomputer-readable medium/memory 1111 via a bus 1121. In certain aspects,the computer-readable medium/memory 1111 is configured to storeinstructions that when executed by processor 1109, cause the processor1109 to perform one or more of the operations illustrated in FIG. 11, orother operations for performing the various techniques discussed herein.

In certain aspects, the processing system 1114 further includes areceiving component 1120 for performing one or more of the operationsillustrated at 1102 in FIG. 11. Additionally, the processing system 1114includes an aligning component 1122 for performing one or more of theoperations illustrated at 1104 in FIG. 11. Further, the processingsystem 1114 includes a mapping component 1124 for performing one or moreof the operations illustrated at 1106 in FIG. 11. Also, the processingsystem 1114 includes a determining component 1126 for performing one ormore of the operations illustrated at 1108 in FIG. 11. Also, theprocessing system 1114 includes a receiving component 1128 forperforming one or more of the operations illustrated at 1110 in FIG. 11.

The receiving component 1120, the aligning component 1122, the mappingcomponent 1124, the determining component 1126, and the receivingcomponent 1128 may be coupled to the processor 1109 via bus 1121. Incertain aspects, receiving component 1120, the aligning component 1122,the mapping component 1124, the determining component 1126, and thereceiving component 1128 may be hardware circuits. In certain aspects,receiving component 1120, the aligning component 1122, the mappingcomponent 1124, the determining component 1126, and the receivingcomponent 1128 may be software components that are executed and run onprocessor 1109.

With respect to determining the location of the RMSI CORESET in thefrequency domain, as described above, the UE may receive a PRB gridoffset and the RMSI CORESET configuration in the PBCH, which, asdescribed above, includes an indication of one or more RMSI frequencyoffset values. The UE may first align the PRB grid of the SSB with thePRB grid of the RMSI CORESET by applying the PRB grid offset. The PRBgrid of the SSB refers to a set of PRBs, which are allocated fortransmitting SSBs, on a larger frequency resource grid that correspondsto the entire frequency bandwidth. Similarly, a PRB grid of the RMSICORESET refers to a set of PRBs, which are allocated for transmittingthe RMSI CORESET, on a larger frequency resource grid that correspondsto the entire frequency bandwidth. The UE may then use the indication todetermine the RMSI CORESET bandwidth as well as the frequency offsetvalues, which provide an indication of the RMSI CORESET frequencylocations with respect to the SSB frequency locations.

For example, in some embodiments, the RMSI CORESET may be time divisionmultiplexed (TDM'd) with the SSB. In some embodiments, the frequencyoffset between RMSI CORESET and SSB (after aligning physical resourceblock (PRB) grid with RMSI CORESET PRB grid using PRB grid offsetsignaled in PBCH) may be the frequency difference from the lowest (i.e.,smallest) PRB (i.e., PRB0) of SSB to the lowest (i.e., smallest) PRB(i.e., PRB0) of RMSI CORESET. As an example, when the PRB grid of theSSB with the PRB grid of the RMSI CORESET are aligned, an offset valueof zero may indicate that the lowest (i.e., smallest) PRB of the SSB andthe lowest (i.e., smallest) PRB of the RMSI CORESET have the same indexnumber or frequency.

Each one of FIGS. 12A-12C illustrates a PRB grid, each including anumber of consecutive SSB PRBs and a number of consecutive RMSI CORESETPRBs. As shown in each of FIGS. 12A-12C, the SSB PRBs and the RMSICORESET PRBs are selected such that they have the maximum number ofoverlapping PRBs. For example, the first column, (column 1202 a, 1202 b,and 1202 c), in each PRB grid illustrates the PRBs (shown as rows) thatinclude SSB PRBs (e.g., shown as shaded in). Each of the remainingcolumns (columns 1204 a, 1204 b, and 1204 c) in each PRB gridillustrates the PRBs that include RMSI CORESET PRBs (e.g., shown asshaded in). The columns going to the right from the first column (e.g.,1202 a, 1202 b, or 1202 c) are ordered from 0, 1, n (as shown in thelast row of the grid which does not correspond to an RB, but is a labelfor the PRB grid), which correspond to the offsets used for determiningthe RMSI CORESET PRBs. The different columns are not meant to implytransmission at different times. As shown, the number of possibleoffsets is every offset value where the RMSI CORESET PRBs completelyoverlaps with the SSB PRBs.

For example, in FIG. 12A, there are 20 SSB PRBs and 24 RMSI CORESETPRBs. The 24 RMSI CORESET PRBs may be selected and transmitted in one offive different scenarios, each corresponding to a certain offset, inorder to maximize the number of overlapping PRBs between the SSB PRBsand the RMSI CORESET PRBs. In the first scenario, the starting PRB(PRB0) of the SSB is the same as the starting PRB of the RMSI CORESET.In such an example, the frequency offset of the RMSI CORESET withrespect to the SSB PRBs is 0 (zero). In the second scenario, the RMSICORESET frequency starts as a PRB below the starting PRB (PRB0) of SSB.In such an example, frequency offset of the RMSI CORESET with respect tothe SSB PRBs is 1. As shown in FIG. 12A, the subcarrier spacing used forthe RMSI CORESET transmission is the same as the subcarrier spacing usedfor the SSB transmission. However, in FIGS. 12B and 12C, the subcarrierspacing (SCS) used for the RMSI CORESET transmission is different thatthe subcarrier spacing used for the SSB transmission. For example, inFIG. 12B, the RMSI SCS is half that of the SSB SCS. In FIG. 12C, theRMSI SCS is twice that of the SSB SCS. Accordingly, in FIG. 12B eachconsecutive of the RMSI CORESET is a shift of the RMSI CORESET infrequency by half the SCS of SSB. Further, in FIG. 12C each consecutiveof the RMSI CORESET is a shift of the RMSI CORESET in frequency by twicethe SCS of SSB. Note that in the embodiments herein, the subcarrierspacing of the RMSI (i.e., Type0-PDCCH common search space) CORESET isdefined by the subcarrier spacing of the PDCCH (e.g., Type0-PDCCH). Inother words, the subcarrier spacing of Type0-PDCCH common search spaceCORESET may be the same as the subcarrier spacing of Type0-PDCCH.

In some embodiments, the frequency offset is in a step of an integermultiple of PRB(s) with respect to RMSI CORESET subcarrier spacing(SCS). In other words, an offset value of a frequency offset is inmultiples of an offset step and is based on at least an offset step sizeand a subcarrier spacing (SCS) of the RMSI CORESET. In some embodiments,an offset value of a frequency offset also depends on the RMSI CORESETbandwidth. In some embodiments, the offset step size depends on the RMSICORESET bandwidth or the SSB SCS or the RMSI SCS or any combinationthereof. An offset step size may be 1 PRB or higher (e.g., 2 PRBs, 6PRBs, 8 PRBs, etc.).

In order for a UE (e.g., 120), that is receiving the RMSI CORESET, to beable to determine the location of the RMSI CORESET frequency resources,in some embodiments, the BS (e.g., 110) may transmit to the UE anindication of the offset values corresponding to the offset between theRMSI CORESET PRBs and the SSB PRBs. This indication may be carried bythe RMSI CORESET configuration in the PBCH, which is carried by a SSB.In such embodiments, knowing the RMSI CORESET SCS, the UE may then use amapping (e.g., such as a hash function, hash map or any other type ofmapping) to map the information contained in the indication to a certainRMSI CORESET BW and offset values. Next, the UE may use the location ofthe SSB's PRBs (which is known to the UE) and apply the offset valuesreceived to determine the location of the RMSI CORESET PRBs.

However, as discussed, there may be a large number of possible frequencyoffset values for the RMSI CORESET depending on the RMSI SCS. FIG. 13illustrates an example table 1300 showing the possible number offrequency offset values that the BS may indicate to the UE in theindication in various scenarios (depending on the RSMI CORE SET SCS andRMSI CORESET BW). As shown, depending on the RMSI CORESET SCS, there maybe a large number of possible frequency offset values for the BS toindicate to the UE. For example, where the RMSI CORESET BW is 24, theSSB BW is 20, and the RMSI CORESET SCS=SSB SCS, then there are 5possible offset values for the RMSI CORESET. Further, where the RMSICORESET BW is 48, the SSB BW is 20, and the RMSI CORESET SCS=SSB SCS,there are 29 possible offset values for the RMSI CORESET. In such cases,if the mapping used by the UE to determine the location of the RMSICORESET PRBs is based on the offset values shown in table 1300, the BSmay accordingly need to use a large number of bits for transmitting anindication to the UE that indicates the offset values and RMSI CORESETBW (e.g., 6-bits to represent the 5+29=34 possible combinations for RMSICORESET SCS=SSB SCS). However, transmitting a large number of bits inthe indication may be suboptimal. Furthermore, for some combinations,some frequency offsets might be excluded from the configuration tofurther reduce the configuration signaling overhead.

Accordingly, in some embodiments, the UE may be configured with amapping that enables the BS to transmit the indication to the UE in amore efficient and less resource-consuming manner. More specifically,the mapping allows for a fewer number of bits to be sent to the UE forindicating the offset values in the indication.

FIG. 14 illustrates an example table 1400 showing a fewer possiblenumber of frequency offset values that the BS may indicate to the UE inthe indication in various scenarios (depending on the RSMI CORESET SCSand RMSI CORESET BW). Accordingly, mapping based on the configurationand offset values shown in table 1400 allows for a fewer number of bitsto be transmitted by the BS in an indication to the UE.

As shown, the table provides different RMSI frequency offset valuesdepending on the SCS of the RMSI CORESET and the SCS of the SSB.However, in comparison with table 1300 of FIG. 13, the offset steps oftable 1400 are larger than the offset steps of table 1300. For example,where RMSI SCS=SSB SCS and the RMSI CORESET bandwidth is 24 PRBs, asshown in FIG. 12A, the offset step may be configured as 2. Accordingly,the offset values may be 0, 2, and 4 (only 3 offset values) in PRBsinstead of 0, 1, 2, 3, and 4, as shown in table 1300. In anotherexample, where RMSI SCS=SSB SCS and the RMSI CORESET bandwidth is 48,the offset step may be 6, as shown. Therefore, the offset values may be0, 6, 12, 18, 24 (only 5 offset values), instead of 0-28 (29 offsetvalues), as shown in table 1300. Accordingly, as described above,configuring the UE and the BS with a mapping based on the configurationand offset values shown in table 1400 enables the transmission of fewerbits to the UE (in the indication carried by the RMSI CORESETconfiguration) while still allowing the UE to determine the offsetvalues. For example, if the mapping used by the UE to determine thelocation of the RMSI CORESET PRBs is based on the offset values shown intable 1400, the BS may accordingly need to use a smaller number of bitsfor transmitting an indication to the UE that indicates the offsetvalues and RMSI CORESET BW (e.g., 3-bits to represent the 3+5=8 possiblecombinations for RMSI CORESET SCS=SSB SCS). These fewer number of bitsmay be what is included in the RMSI CORESET configuration to indicatethe RMSI CORESET BW and offset value for the RMSI CORESET. As discussed,the UE may include a table, hash function, etc., that maps the bitsreceived in the RMSI CORESET configuration to a RMSI CORESET BW andoffset value. In particular, the bits received in the RMSI CORESETconfiguration may not directly correspond to an offset value, meaningthe bit value is not directly the offset value.

In some embodiments, instead of RMSI CORESET and SSB being TDM'd, theRMSI CORESET and SSB may be frequency division multiplexed (FDM'd). FIG.15 shows three examples of how RMSI CORESET may be FDM'd with the SSB.Each column of the rows represents a frequency location (e.g., PRB).Each of the three rows, showing an example of a different way that RMSICORESET can be FDM'd with SSB, represents frequency resources (some ofwhich used for RMSI CORESET and some of which user for SSB) that arereceived by the UE at the same time. As shown, the RMSI CORESET may beFDM'd in the upper frequencies, lower frequencies, or both sides (upperand lower frequencies) of the SSB. For example, RMSI CORESET 1504 a isFMD'd in the upper side of SSB 1502 a in example (a). In example (b),RMSI CORESET 1504 b is FDM'd in the lower side of SSB 1502 b. In example(c), RMSI CORESET 1504 c is FDM'd on both sides of SSB 1502 c.

When the RMSI CORESET is FDM'd with the SSB, the RMSI CORESETconfiguration may include an indication indicative of offset valuescorresponding to the offset between the RMSI CORESET PRBs and the SSBPRBs. This indication carried by the RMSI CORESET configuration in thePBCH. In such embodiments, knowing the RMSI CORESET SCS, the UE may thenuse a mapping (e.g., such as a hash function, hash map or any other typeof mapping) to map the information contained in the indication to acertain RMSI CORESET BW and offset values. Next, the UE may use thelocation of the SSB PRBs resources (which is known to the UE) and applythe offset values received to determine the location of the RMSI CORESETPRBs. In some embodiments, the mapping may be based on exampleconfiguration and offset values shown in table 1600.

FIG. 16 illustrates example table 1600 which shows different offsetvalues depending on whether the RMSI SCS and the SSB SCS are the same ordifferent. For example, where RMSI SCS=SSB SCS and the RMSI CORESETbandwidth is 24, offset values may be −(20+G), {6, 12, 18, 24}+G0. Suchoffset values may indicate that the SSB starts as frequency −20 PRB,followed by a guard period (G), followed by the 24 PRBs of RMSI CORESET,in units of, for example, 6 PRBs (the control channel element (CCE) forPDCCH is 6 PRBs). Similar to the TDM example, in the FDM example, table1600 includes fewer offset values for each particular RMSI SCS and RMSICORESET BW than are physically possible. Accordingly, fewer bits may beused to represent the RMSI CORESET BW and offset values. The UE mayinclude a table, hash function, etc., that maps the bits received in theRMSI CORESET configuration to a RMSI CORESET BW and offset value. Inparticular, the bits received in the RMSI CORESET configuration may notdirectly correspond to an offset value, meaning the bit value is notdirectly the offset value.

In addition to determining the location of the RMSI CORESET in thefrequency domain, the UE may determine the RMSI CORESET time location inthe time domain.

FIG. 17 is a flow diagram illustrating example operations 1700 forwireless communications. Operations 1700 may be performed, for example,by a UE (e.g., UE 120), for determining the location of the RMSI CORESETin the time domain. Operations 1700 begin, at 1702, by storing a mappingof synchronization signal block (SSB) time resources to Type0-physicaldownlink control channel (PDCCH) common search space control resourceset (CORESET) time resources. At 1704, operations 1700 continue byreceiving an indication of the SSB time resources. At 1706, operations1700 continue by determining locations of RMSI CORESET time resourcesbased on the mapping and the indication. At 1708, operations 1700continue by receiving Type0-PDCCH in a Type0-PDCCH common search spaceCORESET.

FIG. 17A illustrates a wireless communications device 1700A that mayinclude various components (e.g., corresponding to means-plus-functioncomponents) configured to perform operations for the techniquesdisclosed herein, such as one or more of the operations illustrated inFIG. 17. The communications device 1700A includes a processing system1714 coupled to a transceiver 1712. The transceiver 1712 is configuredto transmit and receive signals for the communications device 1700A viaan antenna 1713. The processing system 1714 may be configured to performprocessing functions for the communications device 1700A, such asprocessing signals, etc.

The processing system 1714 includes a processor 1709 coupled to acomputer-readable medium/memory 1711 via a bus 1721. In certain aspects,the computer-readable medium/memory 1711 is configured to storeinstructions that when executed by processor 1709, cause the processor1709 to perform one or more of the operations illustrated in FIG. 11, orother operations for performing the various techniques discussed herein.

In certain aspects, the processing system 1714 further includes astoring component 1720 for performing one or more of the operationsillustrated at 1702 in FIG. 17. Additionally, the processing system 1714includes a receiving component 1722 for performing one or more of theoperations illustrated at 1704 in FIG. 17. Further, the processingsystem 1714 includes a determining component 1724 for performing one ormore of the operations illustrated at 1706 in FIG. 17. Also, theprocessing system 1714 includes a receiving component 1726 forperforming one or more of the operations illustrated at 1708 in FIG. 17.

The storing component 1720, the receiving component 1722, thedetermining component 1724, and the receiving component 1726 may becoupled to the processor 1709 via bus 1721. In certain aspects, thestoring component 1720, the receiving component 1722, the determiningcomponent 1724, and the receiving component 1726 may be hardwarecircuits. In certain aspects, the storing component 1720, the receivingcomponent 1722, the determining component 1724, and the receivingcomponent 1726 may be software components that are executed and run onprocessor 1709.

In some embodiments, the RMSI CORESET may be mapped into the downlinktime slots. The mapping of RMSI CORESET into the downlink slots allowsfor flexible multiplexing of time slots with different numerologies aswell as flexible uplink (UL) and downlink (DL) slot switching and UL andDL switching within a time slot. In some embodiments, there may bedifferent options for mapping the RMSI CORESET into the DL slots. Forexample, in some embodiments, RMSI CORESET(s) are mapped into thedownlink slots containing SSB(s) only. In some embodiments, for some SSburst set patterns, RMSI CORESET(s) are first mapped into the downlinkslots containing SSB(s) and then mapped into the downlink slots withoutSSB(s). In some embodiments, for some SS burst set patterns, RMSICORESET(s) are mapped to the downlink slots without SSB(s) only.

In some embodiments, the time location of the RMSI CORESET may bedetermined relative to SSB time location. For example, in someembodiments, there may be a one-to-one mapping or a many-to-one mappingbetween the SSB timing and the RMSI CORESET timing. Once the UE detectsPSS/SSS and decodes PBCH, the UE could infer timing of RMSI CORESETs.

In some embodiments, the RMSI CORESET location in time may be definedrelative to each SSB location. In some embodiments, the RMSI CORESETlocation in time may be defined such that the 1^(st) RMSI CORESET isoffset to the 1^(st) SSB and the following RMSI CORESETs defined with aconfigured distance between RMSI CORESETs. In some embodiments, the RMSICORESET location in time may be a fixed location for each value of RMSIconfiguration table. In some embodiments, RMSI PDCCH monitoring window(containing one or more RMSI CORESET(s) associated with a SSB) timingmay be defined relative to the corresponding SSB timing. In one example,the start timing of the first RMSI PDCCH monitoring window associatedwith first SSB is defined to be relative to the timing of the first SSBtiming, and the timing of other RMSI PDCCH monitoring windows associatedwith the other SSBs are defined to be relative to the timing of firstRMSI PDCCH monitoring window. The relative timing between RMSI PDCCHmonitoring window to the associated SSB can be fixed or signaled to theUE as a part of RMSI configuration. If it is signaled in the RMSIconfiguration, it can be jointly encoded with other information in theconfiguration such as RMSI CORESET configuration.

FIG. 18 illustrates how a collection of FIGS. 18A-18D may be arranged toshow a complete figure including example mappings between the RMSItiming locations and the SSB timing locations for a frequency band below6 GHz. In other words, different portions of FIG. 18 are illustrated byFIGS. 18A-18D and FIG. 18 indicates the correct arrangement of how FIGS.18A-18D may be placed next to each other to create a complete FIG. 18.

These mappings, which may be stored by the UE, enable the UE todetermine the time symbols in which the RMSI CORESET are received basedon the time symbols in which the SSB is received. FIGS. 18A-18Dillustrate different mappings between the RMSI timing locations and theSSB timing locations for different SSB and RMSI CORESET subcarrierspacing (SCS) combinations.

Each column of the mappings shown in FIG. 18A corresponds to a timesymbol. For example, the first column corresponds to time symbol 0 andthe second column corresponds to time symbol 1. Also, each row is shownas an illustration of RMSI CORESET or SSB resources received atdifferent time symbols. As there are 14 time symbols in each time slot,the aggregate of the time resources in columns 0-13 of, for example, row2 corresponds to one time slot (shown in FIGS. 18A and 18B). In anotherexample where the SCSs of SSB and RMSI CORESET are 30 kHz, the aggregateof the time resources in columns 0-13 of row 13 also corresponds to atime slot. In certain aspects, the contents of the SSB and RMSI could beFDM'd together based on the frequency location of the RMSI according tothe embodiments herein.

For example, in embodiments where the SCS of the SSB and the RMSI are 15kHz the mappings between the SSB time symbols and the RMSI CORESET timesymbols are shown by rows 2-5, where the second row shows the locationof the SSB time symbols and rows 3-5 show the location of the RMSICORESET time symbols in relation to the SSB time symbols. Morespecifically, row 3 shows the mapping between the RMSI CORESET timesymbols and the SSB time symbols when the RMSI CORESET is one-symbollong. For example, the second row includes SSB time symbols 2-5 and 8-11in the first time slot (shown in FIGS. 18A-18B) as well as SSB timesymbols 2-5 and 8-9 in the next time slot (shown in FIG. 18B)(collectively shown as SSB block 1810).

Based on the location of the SSB PRBs 1810, the UE may determine thelocation of the RMSI CORESET slots. For example, where the SCSs of SSBand RMSI CORESET are 15 kHz and when the time duration of RMSI CORESETis one symbol long (shown in row 3 of FIG. 18A), the location of thefirst RMSI CORESET time symbol in the first time slot is time symbol 0based on the first SSB transmission occupying time symbols 2-5.Similarly, the location of the second RMSI CORESET time symbol is timesymbol 1, when the second transmission of the SSB in the same time slotoccupies time symbols 8-11. As shown in row 4 of the table, when theRMSI CORESET is 2 symbols long, however, the RMSI CORESET in the firsttime slot occupies time symbols 0 and 1 etc. The different rows (3-5)are not meant to imply transmission at different times or frequencies.They are meant to show the different scenarios where RMSI CORESET may betransmitted with a variety of symbol lengths.

FIG. 19 illustrates how a collection of FIGS. 19A-18B may be arranged toshow a complete figure including example mappings between the RMSItiming locations and the SSB timing locations for a frequency band above6 GHz. Similar to FIG. 18, each column of the mapping of FIG. 19corresponds to a time symbol. For example, the first column correspondsto time symbol 0 and the second column corresponds to time symbol 1.Also each row is shown as an illustration of RMSI CORESET and SSBresources received at different time symbols. However, the contents ofthe SSB and RMSI could be FDM'd together based on the frequency locationof the RMSI according to the embodiments herein.

As an example, where the SCS of the SSB and the RMSI are both 120 kHz,the mappings between the SSB time symbols and the RMSI CORESET timesymbols are shown by rows 11-14 of the table, for when the SSB resourcesare FDM'd together with RMSI CORESET resources, and rows 16-18 of thetable, for when the SSB resources are TDM'd together with RMSI CORESETresources. For example, when the SSB resources are FDM'd together withRMSI CORESET resources, row 11 shows the location of the SSB timesymbols and rows 12-14 show the location of the RMSI CORESET timesymbols in relation to the SSB time slots. The different rows (12-14)are not meant to imply transmission at different times or frequencies.They are meant to show the different scenarios where RMSI CORESET may betransmitted with a variety of symbol lengths.

Example OSI Coreset Offset Design

Parameters, such as frequency location, bandwidth, and numerology, forbroadcast OSI CORESET are the same as those for the corresponding RMSICORESET. In certain aspects, such parameters are identical for RMSICORESETs configured by PBCH in all SSB or PBCH blocks which define acell from the perspective of the UE. It's important to note that the OSICORESET periodicity might, however, be longer than RMSI CORESETperiodicity.

Accordingly, in some embodiments, the UE may determine the location ofthe OSI CORESET in the frequency and time domains based on the locationof the RMSI CORESET in the frequency and time domains. In suchembodiments, the timing offset between OSI CORESET and RMSI CORESET issignaled to the UE (e.g., implicitly or explicitly). An implicitsignaling takes place when the UE is able to infer the locations of boththe RMSI CORESET and the OSI CORESET time resources based on thelocation of the SBB time resources. An explicit signaling takes placewhen the UE is able to infer the locations of the OSI CORESET timeresources based on the location of the RMSI CORESET time resources.Therefore, once the UE acquires RMSI PDCCH successfully, as describedabove, it may infer the corresponding OSI CORESET timing for acquiringOSI PDCCH. In some embodiments, the timing of OSI CORESET may be definedrelative to the SSB timing. This timing may be signaled in RMSI to UE ormay be fixed.

The network may configure CORESET configuration for OSI in RMSI to UE.If no such configuration is signaled to the UE, the UE uses the CORESETconfiguration for RMSI signaled in PBCH.

FIG. 20 is a flow diagram illustrating example operations 2000 forwireless communications. Operations 2000 may be performed, for example,by a UE (e.g., UE 120), for determining the location of the OSI CORESETfrequency resources. Operations 2000 begin, at 2002, by determiningfrequency locations of Type0-physical downlink control channel (PDCCH)common search space control resource set (CORESET) in a physicaldownlink shared channel (PDSCH). At 2004, operations 2000 continue bydetermining frequency locations of Type0a-physical downlink controlcommon search space CORESET in the PDSCH based on the frequencylocations of the Type0-PDCCH common search space CORESET. At 2006,operations 2000 continue by receiving the Type0a-PDCCH common searchspace CORESET.

FIG. 20A illustrates a wireless communications device 2000A that mayinclude various components (e.g., corresponding to means-plus-functioncomponents) configured to perform operations for the techniquesdisclosed herein, such as one or more of the operations illustrated inFIG. 20. The communications device 2000A includes a processing system2014 coupled to a transceiver 2012. The transceiver 2012 is configuredto transmit and receive signals for the communications device 2000A viaan antenna 2013. The processing system 2014 may be configured to performprocessing functions for the communications device 2000A, such asprocessing signals, etc.

The processing system 2014 includes a processor 2009 coupled to acomputer-readable medium/memory 2011 via a bus 2021. In certain aspects,the computer-readable medium/memory 2011 is configured to storeinstructions that when executed by processor 2009, cause the processor2009 to perform one or more of the operations illustrated in FIG. 20, orother operations for performing the various techniques discussed herein.

In certain aspects, the processing system 2014 further includes adetermining component 2020 for performing one or more of the operationsillustrated at 2002 in FIG. 20. Additionally, the processing system 2014includes a determining component 2022 for performing one or more of theoperations illustrated at 2004 in FIG. 20. Further, the processingsystem 2014 includes a receiving component 2024 for performing one ormore of the operations illustrated at 2006 in FIG. 20.

The determining component 2020, the determining component 2022, and thereceiving component 2024 may be coupled to the processor 2009 via bus2021. In certain aspects, the determining component 2020, thedetermining component 2022, and the receiving component 2024 may behardware circuits. In certain aspects, the determining component 2020,the determining component 2022, and the receiving component 2024 may besoftware components that are executed and run on processor 2009.

FIG. 21 is a flow diagram illustrating example operations 2100 forwireless communications. Operations 2000 may be performed, for example,by a UE (e.g., UE 120), for determining the location of the OSI CORESETtime resources. Operations 2000 begin, at 2002, by determining timelocations of remaining minimum system information (RMSI) controlresource set (CORESET) in a physical downlink shared channel (PDSCH). At2004, operations 2000 continue by determining time locations of othersystem information (OSI) CORESET in the PDSCH based on the time andfrequency locations of RMSI CORESET. At 2006, operations 2000 continueby receiving the OSI.

FIG. 21A illustrates a wireless communications device 2100A that mayinclude various components (e.g., corresponding to means-plus-functioncomponents) configured to perform operations for the techniquesdisclosed herein, such as one or more of the operations illustrated inFIG. 21. The communications device 2100A includes a processing system2114 coupled to a transceiver 2112. The transceiver 2112 is configuredto transmit and receive signals for the communications device 2100A viaan antenna 2113. The processing system 2114 may be configured to performprocessing functions for the communications device 2100A, such asprocessing signals, etc.

The processing system 2114 includes a processor 2109 coupled to acomputer-readable medium/memory 2111 via a bus 2121. In certain aspects,the computer-readable medium/memory 2111 is configured to storeinstructions that when executed by processor 2109, cause the processor2109 to perform one or more of the operations illustrated in FIG. 21, orother operations for performing the various techniques discussed herein.

In certain aspects, the processing system 2114 further includes adetermining component 2120 for performing one or more of the operationsillustrated at 2102 in FIG. 21. Additionally, the processing system 2114includes a determining component 2122 for performing one or more of theoperations illustrated at 2104 in FIG. 21. Further, the processingsystem 2114 includes a receiving component 2124 for performing one ormore of the operations illustrated at 2106 in FIG. 21.

The determining component 2120, the determining component 2122, and thereceiving component 2124 may be coupled to the processor 2109 via bus2121. In certain aspects, the determining component 2120, thedetermining component 2122, and the receiving component 2124 may behardware circuits. In certain aspects, the determining component 2120,the determining component 2122, and the receiving component 2124 may besoftware components that are executed and run on processor 2109.

The embodiments described above related to operations performed by a UE.FIG. 22, however, describes operations performed by a base station.

FIG. 22 is a flow diagram illustrating example operations 2200 forwireless communications. Operations 2200 may be performed, for example,by a BS (e.g., BS 110). Operations 2200 begin, at 2202, by transmittinga synchronization signal block (SSB) to a user equipment, the SSBcomprising a physical broadcast channel (PBCH) having a Type0-physicaldownlink control channel (PDCCH) common search space control resourceset (CORESET) configuration and a physical resource block (PRB) gridoffset, the Type0-PDCCH common search space CORESET configurationcomprising an indication indicative of one or more offset valuescorresponding to one or more offsets relating to frequency locations ofType0-PDCCH common search space CORESET resource blocks (PRBs) relativeto frequency locations of PRBs of the SSB. At 2204, operations 2000continue by transmitting a Type0-PDCCH in the Type0-PDCCH common searchspace CORESET for reception by the UE.

FIG. 22A illustrates a wireless communications device 2200A that mayinclude various components (e.g., corresponding to means-plus-functioncomponents) configured to perform operations for the techniquesdisclosed herein, such as one or more of the operations illustrated inFIG. 22. The communications device 2200A includes a processing system2214 coupled to a transceiver 2212. The transceiver 2212 is configuredto transmit and receive signals for the communications device 2200A viaan antenna 2213. The processing system 2214 may be configured to performprocessing functions for the communications device 2200A, such asprocessing signals, etc.

The processing system 2214 includes a processor 2209 coupled to acomputer-readable medium/memory 2211 via a bus 2221. In certain aspects,the computer-readable medium/memory 2211 is configured to storeinstructions that when executed by processor 2209, cause the processor2209 to perform one or more of the operations illustrated in FIG. 22, orother operations for performing the various techniques discussed herein.

In certain aspects, the processing system 2214 further includes atransmitting component 2220 for performing one or more of the operationsillustrated at 2202 and 2204 in FIG. 22.

The transmitting component 2220 may be coupled to the processor 2209 viabus 2221. In certain aspects, the transmitting component 2220 may behardware circuits. In certain aspects, the transmitting component 2220may be software components that are executed and run on processor 2209.

The methods disclosed herein comprise one or more steps or actions forachieving the described method. The method steps and/or actions may beinterchanged with one another without departing from the scope of theclaims. In other words, unless a specific order of steps or actions isspecified, the order and/or use of specific steps and/or actions may bemodified without departing from the scope of the claims.

As used herein, a phrase referring to “at least one of” a list of itemsrefers to any combination of those items, including single members. Asan example, “at least one of: a, b, or c” is intended to cover a, b, c,a-b, a-c, b-c, and a-b-c, as well as any combination with multiples ofthe same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b,b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).

As used herein, the term “determining” encompasses a wide variety ofactions. For example, “determining” may include calculating, computing,processing, deriving, investigating, looking up (e.g., looking up in atable, a database or another data structure), ascertaining and the like.Also, “determining” may include receiving (e.g., receiving information),accessing (e.g., accessing data in a memory) and the like. Also,“determining” may include resolving, selecting, choosing, establishingand the like.

The previous description is provided to enable any person skilled in theart to practice the various aspects described herein. Variousmodifications to these aspects will be readily apparent to those skilledin the art, and the generic principles defined herein may be applied toother aspects. Thus, the claims are not intended to be limited to theaspects shown herein, but is to be accorded the full scope consistentwith the language claims, wherein reference to an element in thesingular is not intended to mean “one and only one” unless specificallyso stated, but rather “one or more.” Unless specifically statedotherwise, the term “some” refers to one or more. All structural andfunctional equivalents to the elements of the various aspects describedthroughout this disclosure that are known or later come to be known tothose of ordinary skill in the art are expressly incorporated herein byreference and are intended to be encompassed by the claims. Moreover,nothing disclosed herein is intended to be dedicated to the publicregardless of whether such disclosure is explicitly recited in theclaims. No claim element is to be construed under the provisions of 35U.S.C. § 112, sixth paragraph, unless the element is expressly recitedusing the phrase “means for” or, in the case of a method claim, theelement is recited using the phrase “step for.”

The various operations of methods described above may be performed byany suitable means capable of performing the corresponding functions.The means may include various hardware and/or software component(s)and/or module(s), including, but not limited to a circuit, anapplication specific integrated circuit (ASIC), or processor. Generally,where there are operations illustrated in figures, those operations mayhave corresponding counterpart means-plus-function components withsimilar numbering.

The various illustrative logical blocks, modules and circuits describedin connection with the present disclosure may be implemented orperformed with a general purpose processor, a digital signal processor(DSP), an application specific integrated circuit (ASIC), a fieldprogrammable gate array (FPGA) or other programmable logic device (PLD),discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general-purpose processor may be a microprocessor, but in thealternative, the processor may be any commercially available processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

If implemented in hardware, an example hardware configuration maycomprise a processing system in a wireless node. The processing systemmay be implemented with a bus architecture. The bus may include anynumber of interconnecting buses and bridges depending on the specificapplication of the processing system and the overall design constraints.The bus may link together various circuits including a processor,machine-readable media, and a bus interface. The bus interface may beused to connect a network adapter, among other things, to the processingsystem via the bus. The network adapter may be used to implement thesignal processing functions of the PHY layer. In the case of a userterminal 120 (see FIG. 1), a user interface (e.g., keypad, display,mouse, joystick, etc.) may also be connected to the bus. The bus mayalso link various other circuits such as timing sources, peripherals,voltage regulators, power management circuits, and the like, which arewell known in the art, and therefore, will not be described any further.The processor may be implemented with one or more general-purpose and/orspecial-purpose processors. Examples include microprocessors,microcontrollers, DSP processors, and other circuitry that can executesoftware. Those skilled in the art will recognize how best to implementthe described functionality for the processing system depending on theparticular application and the overall design constraints imposed on theoverall system.

If implemented in software, the functions may be stored or transmittedover as one or more instructions or code on a computer-readable medium.Software shall be construed broadly to mean instructions, data, or anycombination thereof, whether referred to as software, firmware,middleware, microcode, hardware description language, or otherwise.Computer-readable media include both computer storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another. The processor may beresponsible for managing the bus and general processing, including theexecution of software modules stored on the machine-readable storagemedia. A computer-readable storage medium may be coupled to a processorsuch that the processor can read information from, and write informationto, the storage medium. In the alternative, the storage medium may beintegral to the processor. By way of example, the machine-readable mediamay include a transmission line, a carrier wave modulated by data,and/or a computer readable storage medium with instructions storedthereon separate from the wireless node, all of which may be accessed bythe processor through the bus interface. Alternatively, or in addition,the machine-readable media, or any portion thereof, may be integratedinto the processor, such as the case may be with cache and/or generalregister files. Examples of machine-readable storage media may include,by way of example, RAM (Random Access Memory), flash memory, ROM (ReadOnly Memory), PROM (Programmable Read-Only Memory), EPROM (ErasableProgrammable Read-Only Memory), EEPROM (Electrically ErasableProgrammable Read-Only Memory), registers, magnetic disks, opticaldisks, hard drives, or any other suitable storage medium, or anycombination thereof. The machine-readable media may be embodied in acomputer-program product.

A software module may comprise a single instruction, or manyinstructions, and may be distributed over several different codesegments, among different programs, and across multiple storage media.The computer-readable media may comprise a number of software modules.The software modules include instructions that, when executed by anapparatus such as a processor, cause the processing system to performvarious functions. The software modules may include a transmissionmodule and a receiving module. Each software module may reside in asingle storage device or be distributed across multiple storage devices.By way of example, a software module may be loaded into RAM from a harddrive when a triggering event occurs. During execution of the softwaremodule, the processor may load some of the instructions into cache toincrease access speed. One or more cache lines may then be loaded into ageneral register file for execution by the processor. When referring tothe functionality of a software module below, it will be understood thatsuch functionality is implemented by the processor when executinginstructions from that software module.

Also, any connection is properly termed a computer-readable medium. Forexample, if the software is transmitted from a website, server, or otherremote source using a coaxial cable, fiber optic cable, twisted pair,digital subscriber line (DSL), or wireless technologies such as infrared(IR), radio, and microwave, then the coaxial cable, fiber optic cable,twisted pair, DSL, or wireless technologies such as infrared, radio, andmicrowave are included in the definition of medium. Disk and disc, asused herein, include compact disc (CD), laser disc, optical disc,digital versatile disc (DVD), floppy disk, and Blu-ray® disc where disksusually reproduce data magnetically, while discs reproduce dataoptically with lasers. Thus, in some aspects computer-readable media maycomprise non-transitory computer-readable media (e.g., tangible media).In addition, for other aspects computer-readable media may comprisetransitory computer-readable media (e.g., a signal). Combinations of theabove should also be included within the scope of computer-readablemedia.

Thus, certain aspects may comprise a computer program product forperforming the operations presented herein. For example, such a computerprogram product may comprise a computer-readable medium havinginstructions stored (and/or encoded) thereon, the instructions beingexecutable by one or more processors to perform the operations describedherein. For example, instructions for perform the operations describedherein and illustrated in FIGS. 11, 17, and 20.

Further, it should be appreciated that modules and/or other appropriatemeans for performing the methods and techniques described herein can bedownloaded and/or otherwise obtained by a user terminal and/or basestation as applicable. For example, such a device can be coupled to aserver to facilitate the transfer of means for performing the methodsdescribed herein. Alternatively, various methods described herein can beprovided via storage means (e.g., RAM, ROM, a physical storage mediumsuch as a compact disc (CD) or floppy disk, etc.), such that a userterminal and/or base station can obtain the various methods uponcoupling or providing the storage means to the device. Moreover, anyother suitable technique for providing the methods and techniquesdescribed herein to a device can be utilized.

It is to be understood that the claims are not limited to the preciseconfiguration and components illustrated above. Various modifications,changes and variations may be made in the arrangement, operation anddetails of the methods and apparatus described above without departingfrom the scope of the claims.

What is claimed is:
 1. A method for wireless communications by a userequipment (UE), comprising: identifying a mapping of synchronizationsignal block (SSB) time resources to Type0-physical downlink controlchannel (PDCCH) common search space control resource set (CORESET) timeresources; receiving an indication of SSB time resources; determininglocations of Type0-PDCCH common search space CORESET time resourcesbased on the mapping, the indication, a subcarrier spacing of the SSB, asubcarrier spacing of the Type0-PDCCH common search space CORESET, and atime duration of the Type0-PDCCH common search space CORESET, whereinthe locations of Type0-PDCCH common search space CORESET time resourcescorrespond to downlink time resources that the Type0-PDCCH common searchspace CORESET time resources are multiplexed into; and receivingType0-PDCCH in a Type0-PDCCH common search space CORESET.
 2. The methodof claim 1, wherein determining locations of Type0-PDCCH common searchspace CORESET time resources is further based on frequency resourcesover which the Type0-PDCCH common search space CORESET is transmitted.3. The method of claim 1, wherein the downlink time resources containone or more SSB time resources only.
 4. The method of claim 1, whereinthe mapping comprises a one-to-one mapping between the SSB timeresources and the Type0-PDCCH common search space CORESET timeresources.
 5. The method of claim 1, wherein the mapping comprises amany-to-one mapping between the SSB time resources and the Type0-PDCCHcommon search space CORESET time resources.
 6. An apparatus, comprising:a non-transitory memory comprising executable instructions; and aprocessor coupled to the memory and configured to execute theinstructions to cause the apparatus to: identify a mapping ofsynchronization signal block (SSB) time resources to Type0-physicaldownlink control channel (PDCCH) common search space control resourceset (CORESET) time resources; receive an indication of SSB timeresources; determine locations of Type0-PDDCH common search spaceCORESET time resources based on the mappipng, the indication, asubcarrier spacing of the SSB, a subcarrier spacing of the Type0-PDDCHcommon search space CORESET, and a time duration of the Type0-PDCCHcommon search space CORESET, wherein the locations of Type0-PDCCH commonsearch space CORESET time resources correspond to downlink timeresources that the Type0-PDCCH common search space CORESET timeresources are multiplexed into; and receive Type0-PDCCH in a Type0-PDCCHcommon search space CORESET.
 7. The apparatus of claim 6, whereindetermining locations of Type0-PDCCH common search space CORESET timeresources is further based on frequency resources over which theType0-PDCCH common search space CORESET is transmitted.
 8. The apparatusof claim 6, wherein the downlink time resources contain one or more SSBtime resources only.
 9. The apparatus of claim 6, wherein the mappingcomprises a one-to-one mapping between the SSB time resources and theType0-PDCCH common search space CORESET time resources.
 10. Theapparatus of claim 6, wherein the mapping comprises a many-to-onemapping between the SSB time resources and the Type0-PDCCH common searchspace CORESET time resources.
 11. An apparatus, comprising: means foridentifying a mapping of synchronization signal block (SSB) timeresources to Type0-physicl downlink control channel (PDCCH) commonsearch space control resource set (CORESET) time resources; means forreceiving an indication of SSB time resources; means for determininglocations of Type0-PDCCH common search space CORESET time resourcesbased on the mapping, the indication, a subcarrier spacing of the SSB, asubcarrier spacing of the Type0-PDCCH common search space CORESET, and atime duration of the Type0-PDCCH common search space CORESET, whereinthe locations of Type0-PDCCH common search space CORESET time resourcescorrespond to downlink time resources that the Type0-PDCCH common searchspace CORESET time resources are multiplexed into; and means forreceiving Type0-PDCCH in a Type0-PDCCH common search space CORESET. 12.The apparatus of claim 11, wherein determining locations of Type0-PDCCHcommon search space CORESET time resources is further based on frequencyresources which the Type0-PDCCH common search space CORESET istransmitted.
 13. A non-transitory computer readable medium havinginstructions stored thereon that are executable to: identify a mappingof synchronization signal block (SSB) time resources to Type0- physicaldownlink control channel (PDCCH) common search space control resourceset (CORESET) time resources; receive an indication of SSB timeresources; determine locations of Type0-PDCCH common search spaceCORESET time resources based on the mapping, the indication, asubcarrier spacing of the SSB, a subcarrier spacing of the Type0-PDCCHcommon search space CORESET, and a time duration of the Type0-PDCCHcommon search space CORESET, wherein the locations of Type0-PDCCH commonsearch space CORESET time resources correspond to downlink timeresources that the Type0-PDCCH common search space CORESET timeresources are multiplexed into; and receive Type0-PDCCH in a Type0-PDCCHcommon search space CORESET.
 14. The non-transitory computer readablemedium of claim 13, wherein determining locations of Type0-PDCCH commonsearch space CORESET time resources is further based on frequencyresources which the Type0-PDCCH common search space CORESET istransmitted.
 15. A method for wireless communications by a userequipment (UE), comprising: identifying a mapping of synchronizationsignal block (SSB) time resources to Type0- physical downlink controlchannel (PDCCH) common search space control resource set (CORESET) timeresources; receiving an indication of SSB time resources; determiningtime locations of Type0-PDCCH common search space CORESET time resourcesin a physical downlink shared channel (PDSCH) based on the mapping, theindication, a subcarrier spacing of the SSB, a subcarrier spacing of theType0-PDCCH common search space CORESET, and a time duration of theType0-PDCCH common search space CORESET, wherein the time locationscorrespond to downlink time resources that the Type0-PDCCH common searchspace CORESET time resources are multiplexed into; determining timelocations of Type0a- physical downlink control common search spaceCORESET in the PDSCH based on the time locations of the Type0-PDCCHcommon search space CORESET; and receiving the Type0a-PDCCH commonsearch space CORESET.